Phase detector for a programmable clock synchronizer

ABSTRACT

A phase detector in a programmable clock synchronizer for effectuating data transfer between first circuitry disposed in a first clock domain that is clocked with a first clock signal and second circuitry disposed in a second clock domain that is clocked with a second clock signal. The phase detector includes means for sampling the second clock signal with the first clock signal to generate a sampled clock signal. By tracking movement in a predetermined transition in the sampled clock signal, the phase detector is operable to determine the phase difference between the first and second clock signals.

CLAIM OF PRIORITY UNDER 35 U.S.C. §120 & 37 C.F.R. §1.78

This nonprovisional application is a continuation application claiming the benefit of the following prior United States patent application entitled: “Phase Detector for a Programmable Clock Synchronizer,” application Ser. No. 10/630,298; filed Jul. 30, 2003, in the name(s) of: Richard W. Adkisson, which is hereby incorporated by reference.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application discloses subject matter related to the subject matter disclosed in the following commonly owned co-pending patent applications: (i) “Programmable Clock Synchronizer,” filed Jul. 30, 2003; application Ser. No. 10/630,159 (Docket No. 200207722-2), in the name(s) of: Richard W. Adkisson; (ii) “Controller Arrangement for a Programmable Clock Synchronizer,” filed Jul. 30, 2003; application Ser. No. 10/630,182 (Docket No. 200207723-1), in the name(s) of: Richard W. Adkisson; (iii) “System and Method for Synchronizing Multiple Synchronizer Controllers,” filed Jul. 30, 2003; application Ser. No. 10/629,989 (Docket No. 200207724-1), in the name(s) of: Richard W. Adkisson; (iv) “System and Method for Maintaining a Stable Synchronization State in a Programmable Clock Synchronizer,” filed Jul. 30, 2003; application Ser. No. 10/630,297 (Docket No. 200208008-1), in the name(s) of: Richard W. Adkisson; and (v) “System and Method for Compensating for Skew Between a First Clock Signal and a Second Clock Signal,” filed Jul. 30, 2003; application Ser. No. 10/630,317 (Docket No. 200208009-1), in the name(s) of: Richard W. Adkisson, all of which are incorporated by reference herein.

BACKGROUND

Digital electronic systems, e.g., computer systems, often need to communicate using different interfaces, each running at an optimized speed for increased performance. Typically, multiple clock signals having different frequencies are utilized for providing appropriate timing to the interfaces. Further, the frequencies of such clock signals are generally related to one another in a predetermined manner. For example, a core or system clock running at a particular frequency (F_(C)) may be utilized as a master clock in a typical computer system for providing a time base with respect to a specific portion of its digital circuitry. Other portions of the computer system's digital circuitry (such as a bus segment and the logic circuitry disposed thereon) may be clocked using timing signals derived from the master clock wherein the derived frequencies (F_(D)) follow the relationship: F_(C)/F_(D)≧1.

Because of the asynchronous—although related—nature of the constituent digital circuit portions, synchronizer circuitry is often used in computer systems to synchronize data transfer operations across a clock domain boundary so as to avoid timing-related data errors. Such synchronizer circuitry is typically required to possess low latency (which necessitates precise control of the asynchronous clocks that respectively clock the circuit portions in two different clock domains). Typically, phase-locked loops (PLLs) are utilized in conventional synchronizer circuitry arrangements to produce clocks of different yet related frequencies. The PLLs may have a large amount of input/output (I/O) jitter that results in low frequency phase difference, or skew, between different clocks of the synchronizer circuitry. Accordingly, it is essential to determine the skew between different clocks of the synchronizer circuitry.

SUMMARY

A phase detector is disclosed that provides for detecting phase in a programmable clock synchronizer for effectuating data transfer between first circuitry disposed in a first clock domain that is clocked with a first clock signal and second circuitry disposed in a second clock domain that is clocked with a second clock signal. The phase detector includes means for sampling the second clock signal with the first clock signal to generate a sampled clock signal. By tracking movement in a predetermined transition in the sampled clock signal, the phase detector is operable to determine the phase difference between the first and second clock signals.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts a block diagram of an embodiment of a programmable synchronizer system for effectuating data transfer across a clock boundary;

FIG. 2 depicts a schematic diagram of one embodiment of a phase detector;

FIG. 3 depicts a timing diagram associated with a portion of the phase detector embodiment of FIG. 2; and

FIG. 4 depicts a flow chart of one embodiment of a phase detection method.

DETAILED DESCRIPTION OF THE DRAWINGS

In the drawings, like or similar elements are designated with identical reference numerals throughout the several views thereof, and the various elements depicted are not necessarily drawn to scale. Referring now to FIG. 1, therein is depicted an embodiment of a programmable synchronizer system 100 for effectuating data transfer across a clock boundary between a first clock domain (i.e., “fast clock domain”) having N clock cycles and a second clock domain (e.g., “slow clock domain”) having M clock cycles such that N/M>1. Typically, M=(N−1), and by way of exemplary implementation, the synchronizer system 100 may be provided as part of a computer system for transferring data between a faster core clock domain (e.g., operating with a core clock signal of 250 MHz) and a slower bus clock domain (e.g., operating with a bus clock signal of 200 MHz), with a 5:4 frequency ratio. Accordingly, for purposes of this present patent application, the terms “first clock” and “core clock” will be used synonymously with respect to a fast clock domain; likewise, the terms “second clock” and “bus clock” will be used with respect to a slow clock domain.

A phase-locked loop (PLL) circuit 104 is operable to generate a SYNC pulse 110 and a bus clock (i.e., second clock) signal 108 (designated as bus_clock) based on a core clock (i.e., first clock) signal 106 (designated as core_clock) provided thereto. As will be seen below, the SYNC pulse 110 provides a reference point for coordinating data transfer operations and is driven HIGH when the bus_clock and core_clock signals have coincident rising edges. The two clock signals 106, 108 and SYNC pulse 110 are provided to a synchronizer/controller block 102 that straddles the clock boundary between a first clock domain (i.e., core clock domain) and a second clock domain (i.e., bus clock domain) for effectuating data transfer across the boundary. Reference numerals 103A and 103B refer to circuitry disposed in the first and second clock domains, respectively, e.g., core clock domain logic and bus clock domain logic, that transmit and receive data therebetween as facilitated via synchronizers 105A and 105B, which will be described in greater detail hereinbelow.

Each of the core_clock and bus_clock signals 106, 108 is first provided to a respective clock distribution tree block for generating a distributed clock signal that is provided to various parts of the synchronizer/controller block 102. Reference numeral 112 refers to the clock distribution tree operable with the core_clock signal 106 to generate the distributed core_clock signal, which is labeled as “c” and shown with reference numeral 106′ in FIG. 1. Likewise, reference numeral 114 refers to the clock distribution tree 114 operable with the bus_clock signal 108 to generate the distributed bus_clock signal, which is labeled as “b” and shown with reference numeral 108′ in FIG. 1. As one skilled in the art should readily recognize, the distributed clock signals are essentially the same as the input clock signals. Accordingly, the core_clock signal 106 and its distributed counterpart c 106′ are treated equivalently hereinafter. Also, the bus_clock signal 108 and its distributed counterpart b 108′ are similarly treated as equivalent.

A SYNC sampling logic block 116 is operable responsive to the distributed clock signals 106′, 108′ and SYNC pulse signal 110, to generate a pair of sampled SYNC pulses that are forwarded to appropriate synchronizer controller circuitry. In one embodiment, the sampled SYNC pulses are manufactured as follows. The SYNC pulse 110 is sampled twice by two flip flop (FF) elements (not shown in FIG. 1) that are clocked on the rising edge of the distributed core_clock, c 106′. As may be appreciated, sampling by two FF elements is effective in eliminating metastability associated with the SYNC pulse 110 (possibly arising due to the skew between the input signal, core_clock 106 and the output signal, SYNC 110). The twice-sampled SYNC pulse is designated as “sync” signal 118 in FIG. 1, which is provided to a first synchronizer controller (or, core clock synchronizer controller) 124 operating in the first clock domain.

With respect to the second clock domain (i.e., bus clock domain), the SYNC pulse 110 is sampled in the SYNC sampling logic block 116 by a single FF element (not shown in this FIG.) that is clocked on the rising edge of the distributed bus_clock, b 108′. To signify that the sampling is done using the bus_clock, the sampled SYNC pulse is designated as “sync_B” signal 120, which is provided to a second synchronizer controller 122 operating in the second clock domain, also referred to as the bus clock synchronizer controller in FIG. 1.

The bus clock synchronizer controller 122 is operable responsive to the distributed bus_clock, b 108′, and sampled sync_B pulse 120 to generate a plurality of synchronizer control signals, a portion of which signals are directed to a first synchronizer circuit means 105A operating to control data transfer from first circuitry 103A (i.e., core clock domain logic) to second circuitry 103B (i.e., bus clock domain logic). Reference numeral 132 refers to the signal path of this portion of control signals emanating from the bus clock synchronizer controller 122. Another portion of the synchronizer control signals generated by the bus clock synchronizer controller 122 are directed (via signal path 134) to a second synchronizer circuit means 105B operating to control data transfer from second circuitry 103B to first circuitry 103A. Consistent with the nomenclature used in the present patent application, the first and second synchronizer circuits may also be referred to as core-to-bus synchronizer and bus-to-core synchronizer circuits, respectively. In addition, the bus clock synchronizer controller 122 also generates a set of inter-controller control signals that are provided to the first synchronizer controller 124 (i.e., core clock synchronizer controller) such that both controllers can work together. Reference numeral 128 refers to the signal path of the inter-controller control signal(s) provided to the core clock synchronizer controller 124.

Similar to the operation of the bus clock synchronizer controller 122, the core clock synchronizer controller 124 is operable responsive to the distributed core_clock, c 106′, inter-controller control signals and sampled sync pulse 118 to generate a plurality of synchronizer control signals, a portion of which signals are directed to the first synchronizer circuit means 105A and another portion of which signals are directed to the second synchronizer circuit means 105B. Reference numerals 138 and 140 refer to the respective signal paths relating to these control signals. The core clock synchronizer controller 124 also generates data transmit/receive control signals that are provided to the core clock domain logic 103A via signal path 136 in order that the core clock domain logic 103A knows when it can send data to the bus clock domain logic 103B (i.e., valid TX operations) and when it can receive data from the bus clock domain logic 103B (i.e., valid RX operations).

All control signals from the bus clock synchronizer controller 122 to the first and second synchronizers 105A, 105B are staged through one or more FF elements that are clocked with the distributed bus_clock, b 108′. Likewise, the control signals from the core clock synchronizer controller 124 are staged through a number of FF elements clocked with the distributed core_clock, c 106′, before being provided to the various parts of the synchronizer system 100. Accordingly, as will be seen in greater detail below, the various control signals associated with the synchronizer system 100 may be designated with a signal label that is concatenated with a “_ff” or “_ff_B” suffix to indicate the registration process by the distributed core_clock or the distributed bus_clock.

Moreover, as will be set forth in detail below, a phase detector 130 detects phase differences (i.e., skew) between the two clock signals by operating responsive to the sampled bus_clock and core_clock signals. This information is provided to the core clock synchronizer controller 124, which can compensate for the skew or determine appropriate times to coordinate with the bus clock synchronizer controller 122.

Where the bus clock signal is stable with respect to the SYNC pulse, the inter-controller clock relationship control signals are generated by the bus clock synchronizer controller 122 that provide information as to the frequency ratio of the first and second clock signals, clock sequence information and SYNC delay, which are transmitted to the core clock synchronizer controller 124 for synchronizing its core clock signal in accordance therewith. On the other hand, where the core clock signal is stable with respect to the SYNC pulse, the inter-controller clock relationship control signals are generated by the core clock synchronizer controller 124 for transmission to the bus clock synchronizer 122 so that both synchronizer controllers may be appropriately synchronized. Further, a configuration interface 126, labeled as SYNC_Config in FIG. 1, is provided as part of the programmable synchronizer system 100 for configuring the core clock synchronizer controller 124 so that it may be programmed for different skew tolerances, latencies and modes of operation. In one embodiment, the configuration interface 126 may be implemented as a register having a plurality of bits. In another embodiment, a memory-based setting, e.g., EPROM-stored settings, may be provided as a SYNC configuration interface.

Additional details regarding the various sub-systems described hereinabove may be found in the following commonly owned co-pending patent applications: (i) “Programmable Clock Synchronizer,” filed Jul. 30, 2003; application Ser. No. 10/630,159 (Docket No. 200207722-2), in the name(s) of: Richard W. Adkisson; (ii) “Controller Arrangement for a Programmable Clock Synchronizer,” filed Jul. 30, 2003; application Ser. No. 10/630,182 (Docket No. 200207723-1), in the name(s) of: Richard W. Adkisson; (iii) “System and Method for Synchronizing Multiple Synchronizer Controllers,” filed Jul. 30, 2003; application Ser. No. 10/629,989 (Docket No. 200207724-1), in the name(s) of: Richard W. Adkisson; (iv) “System and Method for Maintaining a Stable Synchronization State in a Programmable Clock Synchronizer,” filed Jul. 30, 2003; application Ser. No. 10/630,297 (Docket No. 200208008-1), in the name(s) of: Richard W. Adkisson; and (v) “System and Method for Compensating for Skew Between a First Clock Signal and a Second Clock Signal,” filed Jul. 30, 2003; application Ser. No. 10/630,317 (Docket No. 200208009-1), in the name(s) of: Richard W. Adkisson, all of which are incorporated by reference herein.

As set forth above and in the cross-referenced U.S. patent applications, the synchronizer system 100 may be programmed for different skew tolerances and latencies, so that data transfer at high speeds can proceed properly even where there is a high skew or requirement of low latency. Further, the synchronizer system 100 can operate with any two clock domains having a ratio of N first clock cycles to M second clock cycles, where N/M≧1.

FIG. 2 depicts one embodiment of a phase detector 200 operable to detect phase differences between the clocks used in the synchronizer system 100. Accordingly, it is functionally analogous to the phase detector block 130 shown in FIG. 1. In general, the phase detector 200 employs the rising and falling edges of the core_clock c 106′ to sample the bus_clock b 108′. In one implementation, the bus_clock b 108′ is sampled by at least one first flip flop (FF) clocked on the rising edge of the core_clock c 106′. As illustrated, flip flops 204 and 206 sample the bus_clock b 108′ with the rising edge of the core_clock c 106′. By employing two flip flops for sampling, the phase detector 200 is operable to decrease metastability. Flip flop 204 asserts the sampled bus_clock b 108′ signal as a cr_ff signal 208 which is sampled by the flip flop 206 and asserted as a pd_b_cr signal 210.

Similarly, the bus_clock b 108′ is sampled by at least one second flip flop clocked on the falling edge of the core_clock c 106′. A third flip flop may be employed in conjunction with the at least one second flip flop to maintain timing. As illustrated, flip flops 212 and 214 sample the bus_clock b 108′ with the falling edge of the core_clock c 106′ (to reduce metastability). Flip flop 212 asserts the sampled bus_clock b 108′ signal as a cf_ff signal 216 which is sampled and asserted by the flip flop 214 as a cf_ff_(—)2 signal 218. A flip flop 220 samples the cf_ff_(—)2 signal with the rising edge of the core_clock c 106′ to ensure timing and asserts a pd_b_cf signal 222.

Upon detecting coincident rising edges between the core_clock c 106′ signal and bus_clock b 108′ signal, either the cr_ff 208 signal will include a one-to-zero transition or the cf_ff signal 216 will include a zero-to-one transition. The phase detector 200 described herein detects phase differences or skew between the clock signals by monitoring and tracking the movement of the one-to-zero and zero-to-one transitions, which in turn depends on the movement of the coincident rising edges of the clock signals. In the illustrated embodiment, the phase detector 200 uses flip flops, as opposed to delay units, in order to minimize latency. It should be appreciated, however, that the phase detector 200 may comprise a variety of digital logic components. Moreover, although the phase detector 200 is described in relation to positive logic, negative logic may also be employed to determine the phase difference.

The pd_b_cr signal 210 and the pd_b_cf signal 222 are forwarded to the core clock synchronizer controller 124 and, in particular, a cycle and sequence generator and a skew state detector of the core clock synchronizer controller 124 in order to compensate for skew. The cycle and sequence generator and skew state detector receive the pd_b_cr signal 210 and the pd_b_cf signal 222 by registering the signals several times and detecting a one-to-zero transition on the pd_b_cr registers or a zero-to-one transition on the pd_b_cf registers. The detection may be registered N+1 times, wherein, for example, N+1 is 5 if 5:4 is the largest ratio detected. Taps are selected off the registers and the “zero tap” is selected from these registers depending on the sync_ratio signal provided by the bus clock synchronizer controller 122. Typically, the zero point is asserted by the skew state detector as a pd_z signal. Further information regarding the pd_b_cr and pd_b_cf signals in relation to the core clock synchronizer controller may be found in the aforementioned U.S. patent applications entitled “System and Method for Maintaining a Stable Synchronization State in a Programmable Clock Synchronizer,” filed Jul. 30, 2003; application Ser. No. 10/630,297 (Docket No. 200208008-1), in the name(s) of: Richard W. Adkisson; and “System and Method for Compensating for Skew Between a First Clock Signal and a Second Clock Signal,” filed Jul. 30, 2003; application Ser. No. 10/630,317 (Docket No. 200208009-1), in the name(s) of: Richard W. Adkisson.

FIG. 3 depicts a timing diagram 300 associated with a portion of the phase detector embodiment 200 of FIG. 2, wherein a clock frequency ratio of 5:4 is exemplified. A cycle count 302 refers to the numbering of core_clock cycles in a particular timing sequence. In particular, the timing diagram 300 illustrates the output of the first rising edge flip flop, i.e., the cr_ff signal 208, and first falling edge flip flop, i.e., the cf_ff signal 216, at the core-to-bus frequency ratio of 5:4. As illustrated, the output of the cr_ff signal 208 and the cf_ff signal 216 includes data blocks comprising 0s, 1s, or indeterminate logic states.

As previously discussed, following the coincident edges of the core clock signal 106′ and the bus clock signal 108′, the one-to-zero transition appears on the cr_ff signal 208 or the zero-to-one transition appears on the cf_ff signal 216. In the illustrated embodiment, the zero-to-one transition is located on the cf_ff signal 216 upon the occurrence of the coincident edges of the core_clock c 106′ and the bus_clock b 108′ at cycle 0, as indicated by the zero-to-one transition markers “T₀₋₁.” The location of the transitions in the sampled clock signals, i.e., pd_b_cr 210 and pd_b_cf 222, is, therefore, indicative of where the coincident edges of the clock signals occur in the clock cycle sequence, which in turn is dependent on the phase difference between the clock signals. The phase detector accordingly provides an indication of the skew between the core_clock c 106′ and the bus_clock b 108′ by monitoring and tracking the movement of the T₀₋₁ or T₁₋₀ transitions in the sampled clock signals. Further, as explained in the aforementioned co-pending U.S. patent applications, the detected transitions are used by the core clock synchronizer controller circuitry to generate appropriate skew states based on the movement of the coincident edges of the clocks and their ratio.

FIG. 4 depicts a method for detecting phase difference between a first clock signal and a second clock signal. At block 400, the second clock signal is sampled with a rising edge of the first clock signal. At block 402, the second clock signal is sampled with a falling edge of the first clock signal. The operation of sampling the second clock signal with a rising edge of said first clock signal may include sampling a bus clock signal with a rising edge of a core clock signal. Similarly, the operation of sampling the second clock signal with a falling edge of the first clock signal may include sampling a bus clock signal with a falling edge of a core clock signal. It should be appreciated that operations of blocks 400 and 402 may occur in parallel. At block 404, a phase difference between the first clock signal and the second clock signal is determined by tracking movement in one-to-zero or zero-to-one transitions in the sampled clock signals. The detected phase difference may accordingly be forwarded to the core clock synchronizer controller as a logic state transition on the sampled clock signal that is indicative of the phase shift.

Although the invention has been particularly described with reference to certain illustrations, it is to be understood that the forms of the invention shown and described are to be treated as exemplary embodiments only. Various changes, substitutions and modifications can be realized without departing from the spirit and scope of the invention as defined by the appended claims. 

1. A method for performing vocoder bypass in a wireless telecommunications network, the method comprising: receiving a first identifier for a first station and a second identifier for a second station; making a first determination that the first identifier identifies a device type of the first station, without performing a database lookup to determine if the first identifier is listed in a database; making a second determination that the second identifier identifies a device type of the second station, without performing a database lookup to determine if the second identifier is listed in the database; and responsive to the first and second determinations, performing vocoder bypass.
 2. The method of claim 1, wherein the step of making the first determination comprises determining whether the first identifier includes a first predetermined aspect indicative of a mobile station; and wherein the step of making the second determination comprises determining whether the second identifier includes a second predetermined aspect indicative of a mobile station.
 3. The method of claim 2, wherein at least one of the first predetermined aspect and the second predetermined aspect comprise an area code extension.
 4. The method of claim 3, wherein the area code extension identifies a network service provider.
 5. The method of claim 2, wherein at least one of the first predetermined aspect and the second predetermined aspect comprise a predetermined area code.
 6. The method of claim 5, wherein the predetermined area code identifies a network service provider.
 7. The method of claim 1, wherein the first identifier comprises a differentiated telephone number for the first station, and the second identifier comprises a differentiated telephone number for the second station.
 8. The method of claim 1 further comprising a computer readable medium having stored therein instructions for causing a processor to execute the steps of the method of claim
 1. 9. The method of claim 1, wherein the device type is a mobile station.
 10. A method carried out at an intermediate entity in communication with a first mobile station and a terminating node, the method comprising: receiving an identifier for the terminating node from the first mobile station via a wireless telecommunications network; determining whether the identifier includes a predetermined aspect that identifies the terminating node as a second mobile station, without performing a database lookup to determine if the identifier is listed in a database; and performing vocoder bypass if the identifier includes the predetermined aspect.
 11. The method of claim 10, wherein the predetermined aspect comprises an area code extension.
 12. The method of claim 10, wherein the predetermined aspect comprises a predetermined area code.
 13. The method of claim 10 further comprising determining a corresponding network service provider based on the predetermined aspect.
 14. The method of claim 13, wherein the step of determining a corresponding network service provider comprises providing the predetermined aspect to a circuit to determine the corresponding network service provider.
 15. The method of claim 10 further comprising a computer readable medium having stored therein instructions for causing a processor to execute the steps of the method of claim
 10. 16. An identifier for use in a wireless telecommunications network, the identifier comprising: a telephone number for a node; and a predetermined aspect, wherein the predetermined aspect identifies whether the node is a mobile station in such a manner that an intermediate entity in the wireless telecommunications network can determine, based on the predetermined aspect, that the node is a mobile station, without performing a database lookup to determine if the telephone number for the node is listed in a database.
 17. The identifier of claim 16, wherein the intermediate entity performs a vocoder bypass if the predetermined aspect identifies the node as a mobile station.
 18. The identifier of claim 16, wherein the predetermined aspect comprises an area code extension.
 19. The identifier of claim 16, wherein the predetermined aspect comprises a predetermined area code.
 20. The identifier of claim 16, wherein the predetermined aspect corresponds to a network service provider for the node.
 21. The identifier of claim 20, wherein the identifier is sent from an initiating mobile station to the intermediate entity, and the intermediate entity performs a vocoder bypass only if the initiating mobile station uses the network service provider. 